Supply item messaging

ABSTRACT

One example discloses a peripheral supply component. The peripheral supply component includes a supply item to provide resources on an installed peripheral component, wherein the supply item is a consumable, upgradable, or replacement component on the installed peripheral component. An encoded component is installed with the supply item, wherein the encoded component is employed to generate a message event related to the peripheral component.

RELATED APPLICATIONS

The present application is a continuation of U.S. National Stage under35 USC 371 patent application Ser. No. 14/114,404 filed on Oct. 28,2013, which claims priority to Serial No. PCT/US2011/34332, filed onApr. 28, 2011, the entirety of both of which are incorporated herein byreference.

BACKGROUND

Computer peripherals come in many forms including printers, copiers, faxmachines, scanners, entertainment devices, and so forth. Not only arethese devices or peripherals connected locally to various computingdevices but they are more than likely connected to a network environmentin conjunction with the respective computing devices, wherein thenetwork is sometimes referred to as a “cloud.” The term “cloud” is usedas a metaphor for the Internet, based on the cloud drawing often used torepresent computer networks. Cloud computing describes a supplement,consumption, and delivery model for information technologies servicesbased on the Internet, and can involve over-the-Internet provision ofdynamically scalable and often virtualized resources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for generating supply enabledmessages.

FIG. 2 illustrates an example of communications triggered from supplyenabled events.

FIG. 3 illustrates an example of generalized supply information fieldsfor supply enabled messages.

FIG. 4 illustrates an example of supply information fields for supplyenabled messages.

FIG. 5 illustrates an example of generalized message classes for supplyenabled messages.

FIG. 6 illustrates an example of message classes for supply enabledmessages.

FIG. 7 illustrates an example of supplies for supply enabled messages.

FIG. 8 illustrates an example of peripherals for supply enabledmessages.

FIG. 9 illustrates a flowchart example of a method for generating supplyenabled messages.

FIG. 10 illustrates an example of a computer system that can be employedto implement the systems and methods illustrated in FIGS. 1-9.

DETAILED DESCRIPTION

FIG. 1 illustrates an example system 100 for generating supply enabledmessages. The system 100 includes a computer peripheral 110 (orperipheral device) that includes a processing unit 120 (or processor)that executes instructions from a memory 124 that includes firmware orother storage media. One or more supply items 130-138 are provided tothe computer peripheral 110 as resources for the peripheral, where thesupply items are labeled 1-N, with N being an integer greater than orequal to 1. Such supply items 130-138 could include replacement items(e.g., ink or toner), upgrade items (e.g., component to addfunctionality to peripheral), or repair items (e.g., replacement forworn or defective components) for example which are described in moredetail below. As shown, each of the respective supply items 130-138 caninclude an encoded message identifier 140 that can be processed by asupply message decoder 150 which in turn generates or triggers messageevents to provide further communications at a network site 160 (e.g.,website) and/or at a local display associated with the peripheral 110.The peripheral 110 can communicate with a computer or computing device180 via a network connection 184 and/or via a local connection 190,wherein the computing device can include software 194 to interact withthe peripheral. For instance, in one example, the message event caninclude forwarding, by the supply message decoder 150, the encodedmessage identifier 140 to the network site 160. The network site 160 canemploy the encoded message identifier 140 to identify a particularmessage for the computer peripheral 110 and/or the computing device 180.

It is noted that the encoded message identifier 140 can be determinedand generated external to the computer peripheral 110. For instance, inconventional peripheral systems, an ink-low message may be generated bythe computer peripheral 110 or computer 180 which is determined anddetected by the peripheral. In contrast, the encoded message identifier140 can be generated external to the peripheral 110 and employed toprovide information that may not and/or cannot be determined by theperipheral itself and thus provides many benefits and utilities whichare described in more detail below. In one example, a peripheralsubsystem is provided. This includes a replaceable or upgradable supplyitem 130-138 to provide a resource to a peripheral device 110. Anencoded message identifier 140 can be installed with the supply item130-138, wherein the encoded message identifier can be employed togenerate a message event related to the peripheral device.

The encoded message identifier 140 can include a reference to a systemor message. The reference could be implemented, for example as numberand/or a bit code to specify a system or a message number to trigger amessage to be displayed. In another example, the encoded messageidentifier 140 includes supply data that triggers the message events,wherein the message events are employed to communicate a message from aperipheral manufacturer, to determine a model number of a targetedperipheral, or determine that a message is to be broadcast to members ofa designated peripheral class. In yet another example, the encodedmessage identifier 140 includes a data value that triggers classes ofmessages.

Classes of messages can be related to differing aspects such as a classcode to indicate no messages are available. Other classes relate towarranty issues, recall issues, repairs, limited supplies availability,or new supply model numbers, for example. Message events generated fromthe encoded message identifiers 140 can trigger communications at anetwork website 160, wherein the communications (bi-directional) caninclude text, images, audio, graphics, and/or video, for example. Therespective message events can also trigger communications at the localdisplay 170 associated with the peripheral 110, wherein thecommunications can also include text, images, audio, graphics, video,and so forth.

As can be appreciated, the supply items 130-138 can include variousitems associated with the peripheral 110 that includes ink, toner, areplacement component, a repair component, or a device upgradecomponent, for example. The supply item 130-138 can be employed with aprinter, a copier, a fax machine, a scanner, a peripheral device, or anentertainment device, for example. In another example aspect, aperipheral system 100 is provided. This includes the memory 124 forstoring computer executable instructions associated with a peripheraldevice 110. A processing unit 110 can also be provided for accessing thememory 124 and executing the computer executable instructions. Suchinstructions can include the supply message decoder 150 to detect anencoded bit stream from a peripheral replacement item or peripheralupgrade item 130-138, wherein the encoded bit streams are employed togenerate messages that are determined external to the peripheral device110 as noted previously. The encoded bit streams can be employed togenerate classes of messages, wherein the classes of messages can berelated to no message, warranty recall, customer repair, limited supplyavailability, or new selectable number, for example.

It is noted that the encoded message identifiers 140 can be in the formof electronic data such as bit streams but mechanical encodings are alsopossible. For example, if a replacement part were added to the system,an indenture or other mechanical feature such as a raised point could beused to trigger an event at the peripheral 110. For instance, twomechanical indents followed by a raised feature (e.g., mechanical coderepresenting 001) on a replacement part could be mechanically detectedand employed to trigger further electronic communications at the networksite 160 and/or locally at 170. The following discussion is related to aspecific example of the system 100. Notably the discussion is related tothe computer peripheral 110 being employed as a printing device but asnoted previously, it is to be appreciated that the computer peripheralis not limited to such example.

After peripheral devices 110 such as printers have been released orsold, manufacturers can become aware of issues and solutions to thoseissues yet have limited means to effectively communicate to those whomay be affected. One problem considers how communications shouldcommence in the future with users—especially those who have nototherwise registered the peripherals. For example, by encoding data onthe supply items 130-138, printer firmware and software can communicateto the user that the manufacturer has identified an issue with theirrespective printer or other device. The user can then be directed to aweb site via a link in the message, for example. The web site, usingdata sent from the printer, can provide details (e.g., text, video, andso forth) to repair printer issues. Issues could include recalls (e.g.,power cords, power supplies, and so forth), customer fixes (e.g., how torepair pick rollers), supply availability (e.g., where to go to findolder supplies), and Selectability Number changes, where alternativesupply information may be provided that provides a different replacementmodel number, for example. It is noted that the term selectabilitynumber can include other types of numbers such as part numbers, forexample.

For warranty recalls, prior solutions allowed contacting customers whoregistered their printer's via mail or e-mail, for example. Recallnotices were also provided on the web but many users do not consult suchresources. Customer repairs can be handled by an agent but automatedmethods for communicating such repairs were lacking. For limitedsupplies availability, there were no suitable methods to identify orinform customers about where to find supplies when fewer stores wereoffering such items. Thus, there is no suitable method of proactivelyand automatically communicating to respective users who may not haveotherwise been previously identified. For selectability number (or partnumber) changes, sellers may attempt to communicate these changes atpoint of sale, but this can be confusing to customers.

By placing encoded data on a supply item 130-138, the manufacturer canbroadcast a message to printers that accept the supply or a singleprinter model within a platform. This supply data can also include areference number to specify to the system which type of message andwhich specific message should be displayed. Supply item data can includebit triggered message identifiers that can be encoded as an integer inthe supply item's bit map, for example. The encoded value can causefirmware and software to provide a tailored message for the type ofissue the manufacturer is attempting to communicate to the user. Encodedsupply data can also enable the printer or other device to determine thespecific model number of the targeted printer or recognize that themessage is a broadcast message for the printers that can accept thesupply.

In one example, the integer encoded in the supply item 130-138 cangenerate classes of messages. These classes can include for example: “NoMessage”, “Warranty Recall”, “Customer Repairs”, “Limited SuppliesAvailability”, and “New Selectability Numbers” among other classdesignations. Thus, printer firmware/software could display a generalmessage for each of these classes of messages (e.g. Warranty Recallmessage could be “There is a Warranty Recall on your printer. Please goto specified location for more information”). These messages are usuallygeneral in nature because at the time the printer is shipped, themanufacturer is generally unaware of potential problems/issues and theyshould have a flexible system to process the unknown.

When the user clicks on the web link triggered from the encoded messageidentifiers, the printer can then pass/communicate information to theweb site. This information can contain data such as Printer ModelNumber, Printer Build Date, Firmware Revision, Supply Bit TriggeredMessage Integer, Supply detail (e.g., color, size, and so forth),country, language, and so forth. The web site uses the informationprovided by the printer or other device/peripheral to determine thespecific message for that printer. These messages could be anything fromtext, text/graphics to video, for example. Together, the Supply,Printer, and Web site provide unique and tailored messaging tocustomers. Using the supply to ‘push’ this type of messaging is animprovement over current methods since all printers use supplies andthus manufacturers can improve the effectiveness of making users awareof issues/changes as they arise.

In some examples, each of the supply items 130-138 can have a uniqueencoded message identifier 140. For instance, in an example wherein thecomputer peripheral 110 is implemented as a color printer that canreceive four different ink cartridges (e.g., black, magenta, cyan andyellow cartridges), each of the supply items 130-138 could beimplemented as an ink cartridge of a specific color. In such asituation, a black ink cartridge could be implemented with a firstencoded message identifier 140, while a color cartridge (e.g., magenta,cyan or yellow) could be implemented with a second encoded messageidentifier 140, different from the first encoded message identifier 140.In such a situation, different network messages 160 could be generatedfor the computer peripheral 110 depending on the particular supply item130-138 installed at the computer peripheral 110.

Some advantages of using the web to ‘host’ the actual messagesinclude: 1. The manufacturer does not know in advance whatproblems/issues they need to solve. Placing the actual message with thesupply item allows flexibility to address issues as they are discoveredversus having to try to anticipate problems/solutions if they had placedthe specific messages in software or Front Panel upon initial shipment;2. Messages/Solutions can be updated on web more easily than insoftware/firmware. The web is often better suited to enablingmulti-media messages (e.g. videos of how to repair a printer issuesverses just text or text/graphics); 3. The manufacturer does not know inadvance what Selectability Numbers (like model numbers) will change toin the future. Having the information on the web allows flexibility tomake unanticipated changes at some point in the future.

As noted previously, the network system 100 can be implemented, forexample, as a computing cloud, where the peripheral 110 can be connectedto the network 184. The network 184 can be implemented, for example, asthe Internet. Nodes on the network 184 can communicate via acommunications protocol, such as Transmission Control Protocol/InternetProtocol (TCP/IP), Internet Protocol version 6 (IPv6), and so forth. Theperipheral 110 can be implemented as a cloud device, for example,wherein the peripheral can be assigned a node address (e.g., an IPaddress) on the network 184, where the peripheral can also beregistered.

For purposes of simplification of explanation, in the present example,different components of the system 100 are illustrated and described asperforming different functions. However, one of ordinary skill in theart will understand and appreciate that the functions of the describedcomponents can be performed by different components, and thefunctionality of several components can be combined and executed on asingle component. The components can be implemented, for example, assoftware (e.g., computer executable instructions), hardware (e.g., anapplication specific integrated circuit), or as a combination of both(e.g., firmware). In other examples, the components could bedistributing among remote devices across the network 184 (e.g., externalweb services).

FIG. 2 illustrates an example of communications triggered from supplyenabled events. At 210, a supply item installation occurs. This couldinclude installing a new ink cartridge in a printer example or a newtoner in a copier example. As noted previously, substantially any typeof peripheral can be employed. At 220, encoded data on the installedsupply item is detected by peripheral firmware (or software). At 230,peripheral software is notified of a potential encoded messageidentifier that has been detected at 230. Peripheral software istypically loaded at a computer that operates the peripheral but thesoftware can also execute at the peripheral. At 240, an InternetProtocol (IP) address is generated that allows a user to select suchaddress to enable further communications regarding the peripheral wherethe supply item is installed. Such messages could also be general innature (not necessarily related to peripheral where supply item wasinstalled) such as an announcement by a manufacturer that some promotionor other feature is available. At 250, when the web site communicationshave been established, peripheral information can be sent by theperipheral automatically to the web site in order to tailorcommunications to the situation detected. It is noted that theperipheral information can include information outside of supplyinformation such as Model Number, Serial Number, error states, statusstates, and so forth for example. At 260, further communications arecommenced with the user if necessary. As noted previously, suchcommunications can be in substantially any form such as text, graphics,audio, video, and so forth. This could include downloading upgrade datato the peripheral such as enhanced software or firmware upgrades for theperipheral.

FIG. 3 illustrates an example of generalized supply information fields300 for supply enabled messages. As shown, the supply information fieldscan include a field of encoded or non-encoded information. For example,one field might specify a code that triggers a warranty message at a website. In another example, the message itself may be contained in thefield or respective fields 300.

FIG. 4 illustrates an example of supply information fields 400 forsupply enabled messages. As shown in the examples at 400, the supplyinformation fields could include bit triggered message identifiers. Forexample, code 1 might be related to warranty information and code 2might be related to repair information, wherein a plurality of variouscodes and messages could be created as can be appreciated. Anothersupply information field 400 might include a code to enable a printer orother peripheral to determine and/or communicate its respective modelnumber. Still yet another information field example might include a codethat enables a broadcast message, for example.

FIG. 5 illustrates an example of generalized message classes 500 orsupply enabled messages. As shown, the messages classes can include amessage related to differing types or categories of messages. Suchclasses 500 could include subclasses (e.g., class=warranty,subclass=rollers). Such classes 500 could also include nested classes(e.g., classes specifying other classes and so forth). As can beappreciated, various combinations of classes, subclasses, and nestedclasses are possible.

FIG. 6 illustrates an example of message classes 600 for supply enabledmessages. These classes 600 can include for example: “No Message”,“Warranty Recall”, “Customer Repairs”, “Limited Supplies Availability”,and “New Selectability Numbers” among other class designations. Thus,peripheral firmware/software could display a general message for each ofthese classes of messages. These messages are usually general in naturebecause at the time the peripheral is shipped, the manufacturer isgenerally unaware of potential problems/issues and they should have aflexible system to process the unknown.

FIG. 7 illustrates an example of supplies 700 for supply enabledmessages. Such supplies 700 could include ink cartridges, tonercartridges, scanner supplies, fax machine supplies, mechanicalcomponents, electrical components, or other components. Substantiallyany item 700 that could be installed can have information (encoded orotherwise) supplied to the respective device where the installationoccurs.

FIG. 8 illustrates an example of peripherals 800 for supply enabledmessages. As shown, such peripherals or other devices 800 could includeprinters, copiers, fax machines, scanners, entertainment devices, and soforth for example. Substantially any device that can receive areplacement or upgrade component can be utilized to receive and furtherprocess supply enabled messages.

In view of the foregoing structural and functional features describedabove, an example method will be better appreciated with reference toFIG. 9. While, for purposes of simplicity of explanation, the examplemethod of FIG. 9 is shown and described as executing serially, it is tobe understood and appreciated that the present examples are not limitedby the illustrated order, as some actions could in other examples occurin different orders and/or concurrently from that shown and describedherein. Moreover, it is not necessary that all described actions beperformed to implement a method.

FIG. 9 illustrates an example method 900 for generating supply enabledmessages. The method 900 could be employed for peripheralcommunications, for example. At 910, the method includes receiving amessage event triggered from a replacement device or upgrade deviceinstallation. The message event can comprise an encoded messageidentifier stored at the replacement or upgrade device. As notedpreviously, such replacement could include providing new supplies suchas ink or toner after they are consumed. This could also includereplacing defective or worn components and include adding components tothe peripheral for upgrades for example. At 920, the method includesinitiating remote network communications from the message event. At 930,the method includes determining at least one message from the messageevent based on the encoded message identifier. For instance, this couldinclude interpreting encoded bit streams for example and utilizing thebit streams to trigger further communications. At 940, the methodincludes enabling display of the at least one message based in part onthe message event. As noted previously, this could include generating alocal display message at the peripheral and/or trigging remote networkcommunications at a website, for example. It is also noted that themessage so generated may be no message where the encoded bit streaminstructs the peripheral that no messages are available. It is notedthat the encoded information (or peripheral device information) caninclude peripheral information outside of supply information (e.g.,Model Number, Serial Number, error states, status states, and so forth).

Other examples of the method 900 include enabling display of the atleast one message at a network website or at a location local to aperipheral. This includes storing the event data on a supply itemassociated with a printer, a copier, a fax machine, a scanner, aperipheral device, or an entertainment device. The method 900 can alsoinclude generating the at least one message to communicate recallinformation, warranty information, repair information, supplyavailability information, or a product name change related toalternative supplies that are available. This can also include decodingmessage classes, wherein the message classes include no messages,warranty recall messages, customer repair messages, limited supplyavailability messages, or alternative number messages to facilitatepurchase of replacement supplies. Another example includes enablingwebsite communications, wherein a peripheral transmits information tothe website. This can include processing the information at the websiteto determine messages for the peripheral, wherein the messages includetext, graphics, images, audio, or video.

FIG. 10 is a schematic block diagram illustrating an example system 1000of hardware components capable of implementing examples disclosed inFIGS. 1-9. The system 1000 can include various systems and subsystems.The system 1000 can be a personal computer, a laptop computer, aworkstation, a computer system, an appliance, an application-specificintegrated circuit (ASIC), a server, a server blade center, a serverfarm, a mobile device, such as a smart phone, a personal digitalassistant, etc.

The system 1000 can include a system bus 1002, a processing unit 1004, asystem memory 1006, memory devices 1008 and 1010, a communicationinterface 1012 (e.g., a network interface), a communication link 1014, adisplay 1016 (e.g., a video screen), and an input device 1018 (e.g., akeyboard and/or a mouse). The system bus 1002 can be in communicationwith the processing unit 1004 and the system memory 1006. The additionalmemory devices 1008 and 1010, such as a hard disk drive, server, standalone database, or other non-volatile memory, can also be incommunication with the system bus 1002. The system bus 1002 operablyinterconnects the processing unit 1004, the memory devices 1006-1010,the communication interface 1012, the display 1016, and the input device1018. In some examples, the system bus 1002 also operably interconnectsan additional port (not shown), such as a universal serial bus (USB)port.

The processing unit 1004 can be a computing device and can include anapplication-specific integrated circuit (ASIC). The processing unit 1004executes a set of instructions to implement the operations of examplesdisclosed herein. The processing unit can include a processor core.

The additional memory devices 1006, 1008 and 1010 can store data,programs, instructions, database queries in text or compiled form, andany other information that can be needed to operate a computer. Thememories 1006, 1008 and 1010 can be implemented as computer-readablemedia (integrated or removable) such as a memory card, disk drive,compact disk (CD), or server accessible over a network. In certainexamples, the memories 1006, 1008 and 1010 can comprise text, images,video, and/or audio.

Additionally, the memory devices 1008 and 1010 can serve as databases ordata storage. Additionally or alternatively, the system 1000 can accessan external system (e.g., a web service) through the communicationinterface 1012, which can communicate with the system bus 1002 and thecommunication link 1014.

In operation, the system 1000 can be used to implement, for example, aclient computer, a printer server, and at least some components ofprinters the can be employed in a system that manages a print job.Computer executable logic for implementing the system 1000 can reside inthe system memory 1006, and/or in the memory devices 1008 and/or 1010 inaccordance with certain examples. The processing unit 1004 executescomputer executable instructions originating from the system memory 1006and the memory devices 1008 and 1010. The term “computer readablemedium” as used herein refers to a medium that participates in providinginstructions to the processing unit 1004 for execution.

Where the disclosure or claims recite “a,” “an,” “a first,” or “another”element, or the equivalent thereof, it should be interpreted to includeone or more than one such element, neither requiring nor excluding twoor more such elements. Furthermore, what have been described above areexamples. It is, of course, not possible to describe every conceivablecombination of components or methods, but one of ordinary skill in theart will recognize that many further combinations and permutations arepossible. Accordingly, the invention is intended to embrace all suchalterations, modifications, and variations that fall within the scope ofthis application, including the appended claims.

What is claimed is:
 1. A peripheral device, comprising: a peripheralsubsystem to receive a replaceable or upgradable supply item including acartridge to provide a printing resource to the peripheral device; and asupply message decoder including circuitry to: receive a message eventin response to a trigger condition being met for the peripheral deviceor the supply item based on a trigger of the message event, wherein amessage identifier is encoded on the supply item and includes thetrigger of the message event; decode the message event; and identify amessage that corresponds to the decoded message event, wherein themessage is hosted remote from the peripheral device on a network deviceidentified by the decoded message event, wherein the message identifierincludes a class code that indicates whether one of a plurality ofdifferent classes of messages is allowable.
 2. The peripheral device ofclaim 1, wherein the supply message decoder includes anapplication-specific integrated circuit (ASIC), wherein the messageevent triggers communications to a network website, and wherein thecommunications include text, images, audio, graphics, or video.
 3. Theperipheral device of claim 1, wherein the message event triggerscommunications at a local display associated with the peripheral device,wherein the communications include text, images, audio, graphics, orvideo.
 4. The peripheral device of claim 1, wherein the supply itemincludes one of an ink cartridge and a toner cartridge, and wherein thesupply message decoder includes computer instructions executable by acomputer processing unit (CPU).
 5. The peripheral device of claim 4,wherein the peripheral device includes a printer.
 6. A method forperipheral communications, comprising: receiving a message eventtriggered in response to a trigger condition being met based on atrigger of the message event, wherein a message identifier is encoded ona replaceable or upgradable supply item of a peripheral device andincludes the trigger of the message event; decoding the message event;determining a message that corresponds to the decoded message event,wherein the message is hosted remote from the peripheral device on anetwork device identified by the decoded message event; and enablingdisplay of the message based on the message event, wherein the messageidentifier includes a class code that indicates whether one of aplurality of different classes of messages is allowable.
 7. The methodof claim 6, further comprising enabling display of the message at anetwork website or at a location local to the peripheral device.
 8. Themethod of claim 6, wherein the peripheral device includes at least oneof a printer, a copier, a fax machine, a scanner, or an entertainmentdevice.
 9. The method of claim 6, further comprising displaying themessage, and wherein the class code characterize at least one of recallinformation, warranty information, repair information, supplyavailability information and a product name change related toalternative supplies that are available.
 10. The method of claim 6,wherein the message event includes a bit triggered message identifierencoded as an integer in a bit map.
 11. The method of claim 6, whereinthe message is generated at a manufacturer external to the peripheraldevice.
 12. The method of claim 6, further comprising: transmitting abroadcast message to the peripheral device.
 13. A computer peripheraldevice comprising: a peripheral subsystem to receive a plurality ofreplaceable or upgradable supply items to provide resources to theperipheral device; a memory to store computer executable instructions;and a processor to access the memory and execute the computer executableinstructions, the computer executable instructions including a supplymessage decoder to: receive a message event in response to a triggercondition being met for the peripheral device or at least one of thesupply items based on a trigger of the message event, wherein a messageidentifier is encoded on at least one of the plurality of supply itemsand includes the trigger of the message event; process the message eventto decode the encoded message identifier; and forward the messageidentifier to a remote network site, wherein the remote network siteemploys the message identifier to identify a message stored at theremote network site corresponding to the message identifier for thecomputer peripheral, wherein the message identifier includes a classcode that triggers classes of messages.
 14. The computer peripheral ofclaim 13, wherein the supply items are each one of an ink cartridge anda toner cartridge.
 15. The computer peripheral of claim 13, wherein themessage is displayed to the user at a network website.
 16. The computerperipheral of claim 13, wherein the message is displayed to the user ata location local to the computer peripheral.
 17. The computer peripheralof claim 13, wherein the message characterizes at least one of recallinformation, warranty information, repair information, supplyavailability information and a product name change related toalternative supplies that are available.
 18. The computer peripheral ofclaim 13, wherein the message event includes a bit triggered messageidentifier encoded as an integer in a bit map.
 19. The computerperipheral of claim 13, wherein the message event is generated at amanufacturer external to the computer peripheral.
 20. The peripheraldevice of claim 1, wherein the message identifier includes one of: anindication whether any message identifier is available or a particularone of the plurality is available.